|
|
 |
|
|
|
|
Report
ReportBuilder
BankTransactionRepository
CustomerManagement <Subsystem Controller>>
Customer
CustomerAuthorization
AccountNumberProcessor <Subsystem Controller>>
AccountNumberComparison
CheckDigits |
|
|
|
|
|
|
|
|
Assessing Traceability upon Refining Use Cases |
|
|
|
|
|
|
|
|
After you examine the list of strong candidate classes in the preceding section, you will probably recognize the classnames as derived from the use cases, for the most part. Keep in mind that not all your classes will be listed in the use cases. However, if they aren't listed, they should definitely be associated in some way with the classes that are. Therefore, every time you refine your use cases, ask yourself two questions: |
|
|
|
|
|
|
|
|
Are each of these classes covered in the description of the use cases? |
|
|
|
|
|
|
|
|
If not, are they used by the classes in the use cases, or do they themselves use the classes in them? |
|
|
|
|
|
|
|
|
Not all your classes have to be directly associated with the classes that participate in the use cases. They can be associated with classes that are, in turn, associated with classes in the use cases. In auditing your use cases, then, make sure there is a noticeable chain of association, such that the chain leads back to the use-case model. This will help you ensure that the user requirements are being properly addressed by the architecture of your Visual Basic application. |
|
|
|
|
|
|
|
|
This chapter builds on what you know about use cases and domain analysis, in general, from Day 2. In particular, you learned about revisiting use cases in your evironment as well as updating the problem statement and the use-case model. This chapter shows you the art of working with end users, business analysts, executives, and project managers. You learned how to incorporate new discoveries about the way end users expect to use your Visual Basic application into the design models. Moreover, you gained insight into preserving the artifacts of use-case analysis and development in general. Finally, you |
|
|
|
|
|